feat(tables): improve view and filter controls - #6725

Summary

This second PR builds on #6724 and completes the table-view control changes. Users can choose which saved view is a table's default via a pin in the Views menu. The Columns menu now matches the Sort menu's typography and icon sizing and stays open across toggles. The filter builder has no Apply or Clear buttons: dropdown and row gestures apply immediately, while typed text commits on Enter or blur.

Filter commits now happen directly in completed user-event handlers, not in an after-render effect. Opening the panel, rerendering it, or refreshing column data does not write anything by itself. The save baseline still seeds from the builder's own reading of the stored filter, so a stored tree the flat builder renders differently is only normalized after the user actually edits a rule.

Autosave hardening:

• An autosave response settling no longer remounts an open filter panel and wipes in-progress text or focus; reapplying an identical view configuration is skipped.
• "Filter by cell value" saves the narrowed filter to the active view.
• A stale update-view response can no longer demote the current default in the cache; a promotion must be fresh versus both its own cached row and the currently pinned row.
• isNull and isNotNull conditions and mixed AND/OR filters round-trip through the builder without being silently dropped or flattened until the user changes them.
• Switching a complete valueless filter to an operator or column that needs a value keeps the saved condition active until the replacement value is committed.

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation
• Other: ___________

Testing

• Five focused suites for the changed surfaces: 46 tests across resource options, the filter panel, views menu, columns menu, and view-mutation hooks.
• Coverage includes commit-on-Enter/blur, incomplete operator transitions preserving the saved filter, passive panel/column refreshes writing nothing, OR and isNull shapes, stale promotion responses leaving the default untouched, and the disabled default pin staying inert.
• bun run lint and bun run lint:check
• bun run check:audits (29 repository policy audits)
• bun run --cwd apps/sim type-check
• bun run apps/sim/scripts/check-block-registry.ts feat/better-table-views-ux
• Review focus: field-commit semantics, autosave reapply behavior while the panel is open, single-default cache state, and menu selection without closing the menus.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

Screenshots/Videos

Not included. DOM interaction tests cover the changed menus and filter-commit behavior.

Post-Deploy Monitoring & Validation

• For 24 hours, monitor table-view update errors and save-error toasts after filter, column, and default-view interactions.
• Validate that selecting "Set as default" leaves exactly one default view and that the chosen view opens after returning to the table.
• Validate that typed filters apply on Enter or blur, persist after leaving the panel, and that opening or passively rerendering a saved view's filter panel writes nothing.
• Treat increased table-view update failures, duplicate defaults, or lost filter state as rollback triggers.
• Owner: Tables feature maintainers. This child PR can be rolled back independently if the new controls regress while the autosave foundation remains healthy.